ATOM Documentation

# Clone the public repo
git clone https://github.com/rush86999/atom.git atom-desktop-private
cd atom-desktop-private

# Remove origin and add your private repo
git remote remove origin
git remote add origin git@github.com:YOUR_ORG/atom-desktop-private.git
git push -u origin main

{
  "productName": "YourAppName",
  "identifier": "com.yourcompany.yourapp",
  "app": {
    "windows": [
      {
        "title": "YourAppName"
      }
    ]
  }
}

npx tauri icon /path/to/your-logo.png

NEXT_PUBLIC_API_URL=https://your-saas-domain.com

{
  "build": {
    "beforeBuildCommand": "NEXT_PUBLIC_API_URL=https://your-saas-domain.com npm run build"
  }
}

63: 
64: ### 3.1. Desktop Bridge & Satellite (Local Node)

The desktop app includes a built-in "Satellite" bridge that allows the SaaS platform to control local tools (Terminal, Browser) securely.

**Features:**
- **Terminal Access**: Remote shell execution (default: enabled).
- **Browser Control**: Playwright-based local browser automation (default: enabled).
- **Granular Permissions**: Users can toggle these features individually in the UI.

**Dependencies:**
The app automatically manages a Python venv in `~/.atom/venv` for the satellite script.

### 3.2. Docker Requirements (Local Only)
The Desktop App supports executing containerized skills locally. However, it **does not bundle a Docker runtime**.

- **Requirement**: Docker Desktop (or Docker Engine) must be installed and running on the user's machine.
- **Behavior**: If Docker is not running, containerized skills will fail to execute. The app does not attempt to install Docker automatically.
- **Guidance**: Ensure your onboarding documentation instructs users to install Docker if they plan to use containerized agent skills.

### 3.3. Tauri Shell Configuration (Sidecar)
65: 
66: To enable the "Sidecar" automation (Python/Node scripts running locally), you must install the shell plugin in your desktop fork:
67: 
68: ```bash
69: # In your desktop fork directory
70: npm install @tauri-apps/plugin-shell
71: ```
72: 
73: And register it in `src-tauri/src/lib.rs` (Tauri v2):
74: ```rust
75: pub fn run() {
76:     tauri::Builder::default()
77:         .plugin(tauri_plugin_shell::init()) // Add this line
78:         .run(tauri::generate_context!())
79:         .expect("error while running tauri application");
80: }
81: ```
82: 
83: ### 4. Build Installers

### 5. Cross-Platform Builds (CI/CD)

Add to `.github/workflows/build-desktop.yml`:

### 6. Code Signing (Production)

#### macOS
1. Get Apple Developer certificate
2. Set `APPLE_CERTIFICATE` and `APPLE_CERTIFICATE_PASSWORD` in CI secrets
3. Configure notarization in `tauri.conf.json`

#### Windows
1. Get code signing certificate (DigiCert, Sectigo, etc.)
2. Set `TAURI_PRIVATE_KEY` and `TAURI_KEY_PASSWORD` in CI secrets

### 7. Auto-Update (Optional)

Configure in `tauri.conf.json`:

Create update endpoint in atom-saas to serve latest versions.

---

## Quick Start Commands